Interdependent Policies

The Interdependent Policies feature allows users to copy policy data from one policy to other policies in the Bridge Specialty Suite, through the configuration of source and target master covers and specified workflow containers that contain the dependent data.

To enable this feature, please contact your Insurity account representative.

Note: Prior to enabling this feature, users should configure the necessary elements, i.e. workflow containers and master covers, in order to copy the data between policies.

Data Transfer Workflow Containers

When the Interdependent Policies feature is enabled for the licensee site, users will have to create various workflow containers to be used as data transfer containers, depending on the type of product configured.

A common use case for the Interdependent Policies feature is to create Excess policies by combining common data from different policies into one. This avoids users having to re-key in data that was previously saved (via manual input or system generation), when multiple policies share common information. For example, an insurance company that supports both Home insurance and Auto insurance policies may have certain data that could be shared between the policies for a client who needs both types of policies.

The data transfer Workflow Containers are designed to hold the artifacts (i.e. fields, panels, and grids) that are to be copied from the source to the target policy, and must be shared to the appropriate workflow containers and then selected in the master cover. The data in the containers represent the artifacts that are copied from the source to the target policies. Note that upon deleting a source policy link, the system uses the data transfer containers to indicate what data to delete from the target policy.

Note: These containers should not contain artifacts (i.e fields, grids) that are shared to the container itself, but rather users should create the artifacts needed in this container directly, to be shared to the final target workflow container and policy.

Field Evaluation Rules, if required , should be configured in the final target workflow container that will be used to import data from the other policies. These are the Post-Import Field Evaluation Rule and Pre-Delete Field Evaluation Rule that are selected on the Interdependent Policies screen when setting up the Master Cover. When a user clicks on Save and Import Policy Data in the Linked Policies modal, the Post-Import FER is evaluated and the appropriate data is copied into the target policy. Similarly, when deleting a source policy link, the system evaluates the Pre-Delete FER to determine what data needs to be deleted from the target. For details on creating FERs, see the Field Evaluation Rules page in the Product Design guide.

Once the source and target workflow containers are created, users must configure the Master Cover. For more details, see the Interdependent Policies page in the Master Covers guide.

Once the Master Cover is configured and set to Live, users can create submissions using the interdependent policies configuration and copy data from multiple policies into a target. For more details, see the Linked Policies page in the Workflow guide.